Rendering 3D captions within real-world environments

ABSTRACT

Aspects of the present disclosure involve a system comprising a computer-readable storage medium storing at least one program and method for rendering three-dimensional captions (3D) in real-world environments depicted in image content. An editing interface is displayed on a client device. The editing interface includes an input component displayed with a view of a camera feed. A first input comprising one or more text characters is received. In response to receiving the first input, a two-dimensional (2D) representation of the one or more text characters is displayed. In response to detecting a second input, a preview interface is displayed. Within the preview interface, a 3D caption based on the one or more text characters is rendered at a position in a 3D space captured within the camera feed. A message is generated that includes the 3D caption rendered at the position in the 3D space captured within the camera feed.

PRIORITY CLAIM

This application is a non-provisional of, and claims the benefit ofpriority under 35 U.S.C. § 119(e) from, U.S. Provisional ApplicationSer. No. 62/771,964, entitled “RENDERING 3D CAPTIONS WITHIN REAL-WORLDENVIRONMENTS,” filed on Nov. 27, 2018, and U.S. Provisional ApplicationSer. No. 62/775,713, entitled “TEXTURE MESH BUILDING,” filed on Dec. 5,2018, both of which are hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure relates generally to visual presentations andmore particularly to rendering virtual objects within a real-worldenvironment captured in a camera feed of a computing device.

BACKGROUND

Augmented reality (AR) refers to supplementing the view of real-worldobjects and environments with computer-generated graphics content.Virtual rendering systems can be used to create, view, and interact withengaging and entertaining AR experiences, in which 3D virtual objectgraphics content appears to be present in the real world. Virtualrendering systems are frequently implemented within mobile devices suchas smartphones and tablets.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numeralsmay describe similar components in different views. To easily identifythe discussion of any particular element or act, the most significantdigit or digits in a reference number refer to the figure number inwhich that element is first introduced. Some embodiments are illustratedby way of example, and not limitation, in the figures of theaccompanying drawings in which:

FIG. 1 is a block diagram showing a messaging system for exchanging data(e.g., messages and associated content) over a network, according toexample embodiments.

FIG. 2 is block diagram illustrating further details regarding amessaging system, according to example embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored inthe database of the messaging server system, according to exampleembodiments.

FIG. 4 is a schematic diagram illustrating a structure of a messagegenerated by a messaging client application for communication, accordingto example embodiments.

FIG. 5 is a schematic diagram illustrating an example access-limitingprocess, in terms of which access to content (e.g., an ephemeralmessage, and associated multimedia payload of data) or a contentcollection (e.g., an ephemeral message story) may be time-limited (e.g.,made ephemeral), according to example embodiments.

FIG. 6 is a block diagram illustrating various components of athree-dimensional (3D) caption system, which may be provided as part ofthe messaging system, according to example embodiments.

FIGS. 7-9 is a flowchart illustrating example operations of the 3Dcaption system in performing a method for generating a message thatincludes a 3D caption, according to example embodiments.

FIGS. 10-14 are interface diagrams that illustrate various interfacesprovided by the messaging system, according to some example embodiments.

FIGS. 15A and 15B are interface diagrams that illustrate variousinterfaces provided by the messaging system, according to some exampleembodiments.

FIGS. 16A-16C are interface diagrams that illustrate various interfacesprovided by the messaging system, according to some example embodiments.

FIGS. 17A-17D are interface diagrams that illustrate various interfacesprovided by the messaging system, according to some example embodiments.

FIGS. 18A and 18B are interface diagrams that illustrate variousinterfaces provided by the messaging system, according to some exampleembodiments.

FIG. 19 is a block diagram illustrating a representative softwarearchitecture, which may be used in conjunction with various hardwarearchitectures herein described, according to example embodiments.

FIG. 20 is a block diagram illustrating components of a machine able toread instructions from a machine-readable medium (e.g., amachine-readable storage medium) and perform any one or more of themethodologies discussed herein, according to example embodiments.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques,instruction sequences, and computing machine program products thatembody illustrative embodiments of the disclosure. In the followingdescription, for the purposes of explanation, numerous specific detailsare set forth in order to provide an understanding of variousembodiments of the inventive subject matter. It will be evident,however, to those skilled in the art, that embodiments of the inventivesubject matter may be practiced without these specific details. Ingeneral, well-known instruction instances, protocols, structures, andtechniques are not necessarily shown in detail.

Traditional virtual rendering systems can be subject to presentationproblems due to environmental conditions, user actions, unanticipatedvisual interruption between a camera and the object being rendered, andthe like. This can cause a virtual object to disappear or otherwisebehave erratically, which breaks the illusion of the virtual objectsbeing present in the real world. For example, a virtual rendering systemmay not present virtual objects in a consistent manner with respect toreal-world items as a user moves about through the real world.

Additionally, conventional virtual rendering systems are often lackingin functionality related to authoring AR content because theseconventional systems are not optimized for the limited display size ofmobile computing devices. As an example, conventional virtual renderingsystems are often limited to predefined 3D virtual objects and do notprovide users with the ability to create or edit these virtual objects.As another example, user interfaces of conventional virtual renderingsystems often require users to navigate between various views or windowsto access certain content-authoring functions. These systems usuallyprovide buttons or other interactive elements to facilitate navigationbetween views and windows, but the buttons and other interactiveelements often utilize much of the available display space, which mayobscure AR content being authored or require a user to navigate to yetanother window or view to inspect the AR content being authored. As aresult, the AR content authoring process provided by conventionalvirtual rendering systems may be a time-consuming and tedious processthat requires users to repeatedly shuffle through various views andwindows to ultimately produce content that may not meet the user'sexpectations.

Aspects of the present disclosure include systems, methods, techniques,instruction sequences, and computing machine program products forcreating virtual three-dimensional (3D) objects, such as a 3D caption,and rendering the virtual 3D objects within a camera feed, as if theyexist in real-world environments. For example, media overlays of 3Dcaptions can be generated by the system and displayed in conjunctionwith real-world environment content (e.g., images and/or video)generated by an image-capturing device (e.g., a digital camera), 3Dcaptions include one or more text characters (e.g., letters, symbols,and/or emojis). Users may use the 3D captioning functionality describedherein to augment image data (e.g., images and/or video) to describe,comment on, or provide additional meaning or context to the real-worldenvironment content. The system includes user interfaces to create andedit 3D captions. These user interfaces improve upon interfaces of priorsystems by providing greater functionality and enhanced mechanisms forinteraction such as by providing a preview of 3D captions that are inprogress as they will be rendered within real-world environments, whichallows users to make any desired modification before committing. Giventhese improvements, the system may be particularly suitable in mobiledevice implementations in which a display screen size is limited.

FIG. 1 is a block diagram showing an example messaging system 100 forexchanging data (e.g., messages and associated content) over a network.The messaging system 100 includes multiple client devices 102, each ofwhich hosts a number of applications including a messaging clientapplication 104. Each messaging client application 104 iscommunicatively coupled to other instances of the messaging clientapplication 104 and a messaging server system 108 via a network 106(e.g., the Internet).

Accordingly, each messaging client application 104 can communicate andexchange data with another messaging client application 104 and with themessaging server system 108 via the network 106. The data exchangedbetween messaging client applications 104, and between a messagingclient application 104 and the messaging server system 108, includesfunctions (e.g., commands to invoke functions) as well as payload data(e.g., text, audio, video, or other multimedia data).

The messaging server system 108 provides server-side functionality viathe network 106 to a particular messaging client application 104. Whilecertain functions of the messaging system 100 are described herein asbeing performed by either a messaging client application 104 or by themessaging server system 108, it will be appreciated that the location ofcertain functionality either within the messaging client application 104or the messaging server system 108 is a design choice. For example, itmay be technically preferable to initially deploy certain technology andfunctionality within the messaging server system 108, but to latermigrate this technology and functionality to the messaging clientapplication 104 where a client device 102 has a sufficient processingcapacity.

The messaging server system 108 supports various services and operationsthat are provided to the messaging client application 104. Suchoperations include transmitting data to, receiving data from, andprocessing data generated by the messaging client application 104. Thisdata may include message content, client device information, geolocationinformation, media annotation and overlays, message content persistenceconditions, social network information, and live event information, asexamples. Data exchanges within the messaging system 100 are invoked andcontrolled through functions available via user interfaces (UIs) of themessaging client application 104.

Turning now specifically to the messaging server system 108, anApplication Program Interface (API) server 110 is coupled to, andprovides a programmatic interface to, an application server 112. Theapplication server 112 is communicatively coupled to a database server118, which facilitates access to a database 120 in which is stored dataassociated with messages processed by the application server 112.

Dealing specifically with the API server 110, this server receives andtransmits message data (e.g., commands and message payloads) between theclient device 102 and the application server 112. Specifically, the APIserver 110 provides a set of interfaces (e.g., routines and protocols)that can be called or queried by the messaging client application 104 inorder to invoke functionality of the application server 112. The APIserver 110 exposes various functions supported by the application server112, including account registration, login functionality, the sending ofmessages, via the application server 112, from a particular messagingclient application 104 to another messaging client application 104, thesending of media files (e.g., images or video) from a messaging clientapplication 104 to the messaging server application 114, and forpossible access by another messaging client application 104, the settingof a collection of media data (e.g., story), the retrieval of suchcollections, the retrieval of a list of friends of a user of a clientdevice 102, the retrieval of messages and content, the adding anddeleting of friends to a social graph, the location of friends within asocial graph, opening an application event (e.g., relating to themessaging client application 104).

The application server 112 hosts a number of applications andsubsystems, including a messaging server application 114, an imageprocessing system 116, and a social network system 122. The messagingserver application 114 implements a number of message processingtechnologies and functions, particularly related to the aggregation andother processing of content (e.g., textual and multimedia content)included in messages received from multiple instances of the messagingclient application 104. As will be described in further detail, the textand media content from multiple sources may be aggregated intocollections of content (e.g., called stories or galleries). Thesecollections are then made available, by the messaging server application114, to the messaging client application 104. Other processor and memoryintensive processing of data may also be performed server-side by themessaging server application 114, in view of the hardware requirementsfor such processing.

The application server 112 also includes an image processing system 116that is dedicated to performing various image processing operations,typically with respect to images or video received within the payload ofa message at the messaging server application 114.

The social network system 122 supports various social networkingfunctions and services, and makes these functions and services availableto the messaging server application 114. To this end, the social networksystem 122 maintains and accesses an entity graph within the database120. Examples of functions and services supported by the social networksystem 122 include the identification of other users of the messagingsystem 100 with which a particular user has relationships or is“following,” and also the identification of other entities and interestsof a particular user.

The application server 112 is communicatively coupled to a databaseserver 118, which facilitates access to a database 120 in which isstored data associated with messages processed by the messaging serverapplication 114.

FIG. 2 is block diagram illustrating further details regarding themessaging system 100, according to example embodiments. Specifically,the messaging system 100 is shown to comprise the messaging clientapplication 104 and the application server 112, which in turn embody anumber of some subsystems, namely an ephemeral timer system 202, acollection management system 204, and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing thetemporary access to content permitted by the messaging clientapplication 104 and the messaging server application 114. To this end,the ephemeral timer system 202 incorporates a number of timers that,based on duration and display parameters associated with a message, orcollection of messages (e.g., a story), selectively display and enableaccess to messages and associated content via the messaging clientapplication 104. Further details regarding the operation of theephemeral timer system 202 are provided below.

The collection management system 204 is responsible for managingcollections of media (e.g., collections of text, image, video, and audiodata). In some examples, a collection of content (e.g., messages,including images, video, text, and audio) may be organized into an“event gallery” or an “event story.” Such a collection may be madeavailable for a specified time period, such as the duration of an eventto which the content relates. For example, content relating to a musicconcert may be made available as a “story” for the duration of thatmusic concert. The collection management system 204 may also beresponsible for publishing an icon that provides notification of theexistence of a particular collection to the user interface of themessaging client application 104.

The collection management system 204 furthermore includes a curationinterface 208 that allows a collection manager to manage and curate aparticular collection of content. For example, the curation interface208 enables an event organizer to curate a collection of contentrelating to a specific event (e.g., delete inappropriate content orredundant messages). Additionally, the collection management system 204employs machine vision (or image recognition technology) and contentrules to automatically curate a content collection. In certainembodiments, compensation may be paid to a user for inclusion ofuser-generated content into a collection. In such cases, the curationinterface 208 operates to automatically make payments to such users forthe use of their content.

The annotation system 206 provides various functions that enable a userto annotate or otherwise modify or edit media content associated with amessage. For example, the annotation system 206 provides functionsrelated to the generation and publishing of media overlays for messagesprocessed by the messaging system 100. The annotation system 206operatively supplies a media overlay (e.g., a filter or lens) to themessaging client application 104. In another example, the annotationsystem 206 operatively supplies a media overlay to the messaging clientapplication 104 based on other information, such as social networkinformation of the user of the client device 102. A media overlay mayinclude audio and visual content and visual effects. Examples of audioand visual content include pictures, texts, logos, animations, and soundeffects. An example of a visual effect includes color overlaying.

The audio and visual content or the visual effects can be applied to amedia content item (e.g., a photo) at the client device 102. Forexample, the media overlay including text that can be overlaid on top ofan image or video generated by the client device 102. In anotherexample, the media overlay includes an identification of a locationoverlay (e.g., Venice beach), a name of a live event, or a name of amerchant overlay (e.g., Beach Coffee House).

The annotation system 206 includes a 3D caption system 210 that providesfunctionality to generate, display, and track virtual objects atpositions relative to the client device 102, within a 3D space capturedwithin a camera feed of the client device 102 (also referred to by thoseof ordinary skill in the art as a “camera stream,” “a video stream,” ora “video feed”). The virtual objects generated, displayed, and trackedby the 3D caption system 210 include 3D captions. A 3D caption is a 3Drepresentation of one or more text characters (e.g., letters, symbols,and emojis).

The 3D caption system 210 provides functionality to enable users toauthor, edit, and preview 3D captions. To this end, the 3D captionsystem 210 includes an editing interface 212 and a preview interface214. The editing interface 212 allows a user to author and edit a 3Dcaption. The editing interface 212 enables users to author 3D captionsusing keyboard input and enable users to edit 3D captions using keyboardinput and other types of input including touchscreen-based gestures. Thepreview interface 214 allows a user to preview and review a 3D captionbefore generating a message that includes the 3D caption. The previewinterface 214 may also enable the user to edit the presentation of the3D captions (e.g., by changing a scale, orientation, placement, font, orcolor of the 3D caption).

The 3D caption system 210 may cause a 3D caption to be displayed (e.g.,on a display of the client device 102) at position in a 3D spacecaptured within the camera feed based on a reference surface (e.g., theground) detected in the 3D space. As will be discussed in further detailbelow, the 3D caption system 210 comprises a redundant tracking systemcomprising a set of tracking subsystems configured to track a 3D captionat position in 3D space based on a set of tracking indicia, andtransition between tracking subsystems. The 3D caption system 210 mayfurther transition between tracking with six degrees of freedom (6DoF)and tracking with three degrees of freedom (3DoF) based on anavailability of the tracking indicia.

FIG. 3 is a schematic diagram 300 illustrating data, which may be storedin the database 120 of the messaging server system 108, according tocertain example embodiments. While the content of the database 120 isshown to comprise a number of tables, it will be appreciated that thedata could be stored in other types of data structures as anobject-oriented database).

The database 120 includes message data stored within a message table314. An entity table 302 stores entity data, including an entity graph304. Entities for which records are maintained within the entity table302 may include individuals, corporate entities, organizations, objects,places, events, and so forth. Regardless of type, any entity regardingwhich the messaging server system 108 stores data may be a recognizedentity. Each entity is provided with a unique identifier, as well as anentity type identifier (not shown).

The entity graph 304 furthermore Mores information regardingrelationships and associations between entities. Such relationships maybe social, professional (e.g., work at a common corporation ororganization), interested-based, or activity-based, merely for example.

The database 120 also stores annotation data, in the example form offilters and lenses, in an annotation table 312. Filters and lens forwhich data is stored within the annotation table 312 are associated withand applied to videos (for which data is stored in a video table 310)and/or images (for which data is stored in an image table 308). Filtersare overlays that are displayed as overlaid on an image or video duringpresentation to a recipient user. Lenses include real-time visualeffects and/or sounds that may be added to real-world environmentsdepicted in a camera feed (e.g., while a user is viewing the camera teedvia one or more interfaces of the messaging system 100, while composinga message, or during presentation to a recipient user). In comparison,filters are applied to an image or video after the image or video iscaptured at the client device 102 while a lens is applied to the camerafeed of the client device 102 such that when an image or videos iscaptured at the client device 102 with a lens applied, the applied lensis incorporated as part of the image or video that is generated. Filtersand lenses may be of various types, including user-selected filters andlens from a gallery of filters or a gallery of lenses presented to asending user by the messaging client application 104 when the sendinguser is composing a message.

As mentioned above, the video table 310 stores video data which, in oneembodiment, is associated with messages for which records are maintainedwithin the message table 314. Similarly, the image table 308 storesimage data associated with messages for which message data is stored inthe entity table 302. The entity table 302 may associate variousannotations from the annotation table 312 with various images and videosstored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages andassociated image, video, or audio data, which are compiled into acollection (e.g., a story or a gallery). The creation of a particularcollection may be initiated by a particular user (e.g., each user forwhich a record is maintained in the entity table 302). A user may createa “personal story” in the form of a collection of content that has beencreated and sent/broadcast by that user. To this end, the UI of themessaging client application 104 may include an icon that isuser-selectable to enable a sending user to add specific content to hisor her personal story.

A collection may also constitute a “live story,” which is a collectionof content from multiple users that is created manually, automatically,or using a combination of manual and automatic techniques. For example,a “live story” may constitute a curated stream of user-submitted contentfrom various locations and events. Users whose client devices havelocation services enabled and are at a common location event at aparticular time may, for example, be presented with an option, via auser interface of the messaging client application 104, to contributecontent to a particular live story. The live story may be identified tothe user by the messaging client application 104, based on his or herlocation. The end result is a “live story” told from a communityperspective.

A further type of content collection is known as a “location story,”which enables a user whose client device 102 is located within aspecific geographic location (e.g., on a college or university campus)to contribute to a particular collection. In some embodiments, acontribution to a location story may require a second degree ofauthentication to verify that the end user belongs to a specificorganization or other entity (e.g., is a student on the universitycampus).

FIG. 4 is a schematic diagram illustrating a structure of a message 400,according to some in some embodiments, generated by a messaging clientapplication 104 for communication to a further messaging clientapplication 104 or the messaging server application 114. The content ofa particular message 400 is used to populate the message table 314stored within the database 120, accessible by the messaging serverapplication 114. Similarly, the content of a message 400 is stored inmemory as “in-transit” or “in-flight” data of the client device 102 orthe application server 112. The message 400 is shown to include thefollowing components:

-   -   A message identifier 402: a unique identifier that identifies        the message 400.    -   A message text payload 404: text, to be generated by a user via        a user interface of the client device 102 and that is included        in the message 400.    -   A message image payload 406: image data, captured by a camera        component of a client device 102 or retrieved from memory of a        client device 102, and that is included in the message 400.    -   A message video payload 408: video data, captured by a camera        component or retrieved from a memory component of the client        device 102 and that is included in the message 400.    -   A message audio payload 410: audio data, captured by a        microphone or retrieved from the memory component of the client        device 102, and that is included in the message 400.    -   A message annotations 412: annotation data filters, stickers or        other enhancements) that represents annotations to be applied to        message image payload 406, message video payload 408, or message        audio payload 410 of the message 400.    -   A message duration parameter 414: parameter value indicating, in        seconds, the amount of time for which content of the message        (e.g., the message image payload 406, message video payload 408,        message audio payload 410) is to be presented or made accessible        to a user via the messaging client application 104.    -   A message geolocation parameter 416: geolocation data (e.g.,        latitudinal and longitudinal coordinates) associated with the        content payload of the message. Multiple message geolocation        parameter 416 values may be included in the payload, with each        of these parameter values being associated with respect to        content items included in the content (e.g., a specific image        into within the message image payload 406, or a specific video        in the message video payload 408).    -   A message story identifier 418: identifier value identifying one        or more content collections (e.g., “stories”) with which a        particular content item in the message image payload 406 of the        message 400 is associated. For example, multiple images within        the message image payload 406 may each be associated with        multiple content collections using identifier values,    -   A message tag 420: each message 400 may be tagged with multiple        tags, each of which is indicative of the subject matter of        content included in the message payload. For example, where a        particular image included in the message image payload 406        depicts an animal (e.g., a lion), a tag value may be included        within the message tag 420 that is indicative of the relevant        animal. Tag values may be generated manually, based on user        input, or may be automatically generated using, for example,        image recognition.    -   A message sender identifier 422: an identifier (e.g., a        messaging system identifier, email address, or device        identifier) indicative of a user of the client device 102 on        which the message 400 was generated and from which the message        400 was sent.    -   A message receiver identifier 424: an identifier (e.g., a        messaging system identifier, email address or device identifier)        indicative of a user of the client device 102 to which the        message 400 is addressed.

The contents (e.g., values) of the various components of message 400 maybe pointers to locations in tables within which content data values arestored. For example, an image value in the message image payload 406 maybe a pointer to (or address of) a location within an image table 308.Similarly, values within the message video payload 408 may point to datastored within a video table 310, values stored within the messageannotations 412 may point to data stored in an annotation table 312,values stored within the message story identifier 418 may point to datastored in a story table 306, and values stored within the message senderidentifier 422 and the message receiver identifier 424 may point to userrecords stored within an entity table 302.

FIG. 5 is a schematic diagram illustrating an access-limiting process500, in terms of which access to content (e.g., an ephemeral message502, and associated multimedia payload of data) or a content collection(e.g., an ephemeral message story 504), may be time-limited (e.g., madeephemeral).

An ephemeral message 502 is shown to be associated with a messageduration parameter 506, the value of which determines an amount of timethat the ephemeral message 502 will be displayed to a receiving user ofthe ephemeral message 502 by the messaging client application 104. Inone embodiment, where the messaging client application 104 is aapplication client, an ephemeral message 502 is viewable by a receivinguser for up to a maximum of 10 seconds, depending on the amount of timethat the sending user specifies using the message duration parameter506.

The message duration parameter 506 and the message receiver identifier424 are shown to be inputs to a message timer 512, which is responsiblefor determining the amount of time that the ephemeral message 502 isshown to a particular receiving user identified by the message receiveridentifier 424. In particular, the ephemeral message 502 will only beshown to the relevant receiving user for a time period determined by thevalue of the message duration parameter 506. The message timer 512 isshown to provide output to a more generalized ephemeral timer system202, which is responsible for the overall timing of display of content(e.g., an ephemeral message 502) to a receiving user.

The ephemeral message 502 is shown in FIG. 5 to be included within anephemeral message story 504 (e.g., a personal story, or an event story).The ephemeral message story 504 has an associated story durationparameter 508, a value of which determines a time-duration for which theephemeral message story 504 is presented and accessible to users of themessaging system 100. The story duration parameter 508, for example, maybe the duration of a music concert, where the ephemeral message story504 is a collection of content pertaining to that concert.Alternatively, a user (either the owning user or a curator user) mayspecify the value for the story duration parameter 508 when performingthe setup and creation of the ephemeral message story 504.

Additionally, each ephemeral message 502 within the ephemeral messagestory 504 has an associated story participation parameter 510, a valueof which determines the duration of time for which the ephemeral message502 will be accessible within the context of the ephemeral message story504. Accordingly, a particular ephemeral message story 504 may “expire”and become inaccessible within the context of the ephemeral messagestory 504, prior to the ephemeral message story 504 itself expiring interms of the story duration parameter 508. The story duration parameter508, story participation parameter 510, and message receiver identifier424 each provide input to a story timer 514, which operationallydetermines, firstly, whether a particular ephemeral message 502 of theephemeral message story 504 will be displayed to a particular receivinguser and, if so, for how long. Note that the ephemeral message story 504is also aware of the identity of the particular receiving user as aresult of the message receiver identifier 424.

Accordingly, the story timer 514 operationally controls the overalllifespan of an associated ephemeral message story 504, as well as anindividual ephemeral message 502 included in the ephemeral message story504. In one embodiment, each and every ephemeral message 502 within theephemeral message story 504 remains viewable and accessible for atime-period specified by the story duration parameter 508. In a furtherembodiment, a certain ephemeral message 502 may expire, within thecontext of ephemeral message story 504, based on a story participationparameter 510. Note that a message duration parameter 506 may stilldetermine the duration of time for which a particular ephemeral message502 is displayed to a receiving user, even within the context of theephemeral message story 504. Accordingly, the message duration parameter506 determines the duration of time that a particular ephemeral message502 is displayed to a receiving user, regardless of whether thereceiving user is viewing that ephemeral message 502 inside or outsidethe context of an ephemeral message story 504.

The ephemeral timer system 202 may furthermore operationally remove aparticular ephemeral message 502 from the ephemeral message story 504based on a determination that it has exceeded an associated storyparticipation parameter 510. For example, when a sending user hasestablished a story participation parameter 510 of 24 hours fromposting, the ephemeral timer system 202 will remove the relevantephemeral message 502 from the ephemeral message story 504 after thespecified 24 hours. The ephemeral tinier system 202 also operates toremove an ephemeral message story 504 either message 502 within theephemeral message story 504 has expired, or when the ephemeral messagestory 504 itself has expired in terms of the story duration parameter508.

In certain use cases, a creator of a particular ephemeral message story504 may specify an indefinite story duration parameter 508. In thiscase, the expiration of the story participation parameter 510 for thelast remaining ephemeral message 502 within the ephemeral message story504 will determine when the ephemeral message story 504 itself expires.In this case, a new ephemeral message 502, added to the ephemeralmessage story 504, with a new story participation parameter 510,effectively extends the life of an ephemeral message story 504 to equalthe value of the story participation parameter 510.

Responsive to the ephemeral timer system 202 determining that anephemeral message story 504 has expired (e.g., is no longer accessible),the ephemeral timer system 202 communicates with the messaging system100 (and, for example, specifically the messaging client application104) to cause an indicium (e.g., an icon) associated with the relevantephemeral message story 504 to no longer be displayed within a userinterface of the messaging client application 104. Similarly, when theephemeral timer system 202 determines that the message durationparameter 506 for a particular ephemeral message 502 has expired, theephemeral timer system 202 causes the messaging client application 104to no longer display an indicium (e.g., an icon or textualidentification) associated with the ephemeral message 502.

FIG. 6 is a block diagram illustrating functional components of the 3Dcaption system 210 that configure the 3D caption system 210 to render 3Dcaptions in a 3D space (e.g., a real-world environment) depicted in alive camera teed. The 3D caption system 210 is shown as including arendering component 602, a tracking system 604, and a disruptiondetection component 606. The various components of the 3D caption system210 may be configured to communicate with each other (e.g., via a bus,shared memory, or a switch). Although not illustrated in FIG. 6, in someembodiments, the 3D caption system 210 may include or may be incommunication with a camera configured to produce a camera feedcomprising image data that includes a sequence of images (e.g., avideo).

Any one or more of the components described may be implemented usinghardware alone (e.g., one or more of the processors 608 of a machine) ora combination of hardware and software. For example, any componentdescribed of the 3D caption system 210 may physically include anarrangement of one or more of the processors 608 (e.g., a subset of oramong the one or more processors of the machine) configured to performthe operations described herein for that component. As another example,any component of the 3D caption system 210 may include software,hardware, or both, that configure an arrangement of one or moreprocessors 608 (e.g., among the one or more processors of the machine)to perform the operations described herein for that component.Accordingly, different components of the 3D caption system 210 mayinclude and configure different arrangements of such processors 608 or asingle arrangement of such processors 608 at different points in time.

Moreover, any two or more components of the 3D caption system 210 may becombined into a single component, and the functions described herein fora single component may be subdivided among multiple components.Furthermore, according to various example embodiments, componentsdescribed herein as being implemented within a single machine, database,or device may be distributed across multiple machines, databases, ordevices.

The tracking system 604 may comprise a first tracking sub-system 604A, asecond tracking sub-system 604B, and a third tracking sub-system 604C.Each tracking sub-system tracks the position of a 3D caption within the3D space based on a set of tracking indicia.

Tracking systems are subject to frequent tracking failure due toenvironmental conditions, user actions, unanticipated visualinterruption between camera and object/scene being tracked, and soforth. Traditionally, such tracking failures would cause a disruption inthe presentation of virtual objects in a 3D space. For example, avirtual object may disappear or otherwise behave erratically, therebyinterrupting the illusion of the virtual object being presented withinthe 3D space. This undermines the perceived quality of the 3D experienceas a whole.

Traditional tracking systems rely on a single approach (Natural FeatureTracking (NFT), Simultaneous Localization And Mapping (SLAM),Gyroscopic, etc.) that each have breaking points in real-world usage dueto inaccurate sensor data, movement, loss or occlusion of visual marker,or dynamic interruptions to a scene. Further, each approach may haveindividual limitations in capability. For example, a gyroscopic trackingsystem can only track items with 3DoF. Further, utilization of a singletracking system provides inaccurate or unstable position estimation, dueto inherent limitations of each individual system. For example, an NFTsystem may not provide sufficient pitch, yaw, or roll estimation due tothe inaccuracies of visual tracking alone, while gyroscopic trackingsystems provide inaccurate translation (up, down, left, right).

To address the foregoing issues with traditional tracking systems, the3D caption system 210 comprises multiple redundant tracking sub-systems604A-C that enable seamless transitions between tracking sub-systems.The multiple redundant tracking sub-systems 604A-C address the issueswith traditional tracking systems by merging multiple trackingapproaches into a single tracking system 604. The tracking system 604 isable to combine 6DoF and 3DoF tracking techniques through combining andtransitioning between multiple tracking systems based on theavailability of tracking indicia tracked by the tracking systems. Thus,as the indicia tracked by any one tracking system becomes unavailable,the 3D caption system 210 seamlessly switches between tracking in 6DoFand 3DoF, thereby providing the user with an uninterrupted experience.For example, in the case of visual tracking systems (e.g., NFT, SLAM),tracking indicia typically analyzed to determine orientation may bereplaced with gyroscopic tracking indicia from a gyroscopic trackingsystem. This would thereby enable transitioning between tracking in 6Dofand 3DoF based on the availability of tracking indicia.

In some example embodiments, to transition between tracking in 6DoF and3DoF, the 3D caption system 210 gathers and stores tracking indiciawithin a tracking matrix that includes translation indicia (e.g., up,down, left, right) and rotation indicia (e.g., pitch, yaw, roll). Thetranslation indicia gathered by an NFT system may thereby be extractedfrom the tracking matrix and utilized when future translation indiciagathered by the NFT system become inaccurate or unavailable. In themeantime, the rotation indicia continue to be provided by the gyroscope.In this way, when the mobile device loses tracking indicia, the trackedobjects that are presented in the 3D space will not be changed abruptlyat the frame when the tracking indicia are lost. Subsequently, when thetarget tracking object reappears in the screen, and a new translation T₁is obtained, the translation part of the view matrix will then be takingadvantage of the new translation T₁, and use T₁-T₀ as the translation ofthe view matrix.

The rendering component 602 of the 3D caption system 210 is configuredto generate and render 3D captions in a 3D space captured within a livecamera feed produced by a camera. For example, the rendering component602 may generate a 3D caption based on input received from a user (e.g.,keyboard input) and render the 3D caption in the 3D space capturedwithin the live camera feed. In rendering the 3D caption, the 3D captionsystem 210 assigns the 3D caption to a position in the 3D space based ona real-world reference surface detected in the 3D space.

The 3D caption system 210 may thereafter track the position of the 3Dcaption relative to a user device in the 3D space by one or moretracking systems in 6DoF. For example, the one or more tracking systemsof the 3D caption system 210 may collect and analyze a set of trackingindicia (e.g., roll, pitch, yaw, natural features, etc.) in order totrack the position of the 3D caption relative to the user device in the3D space with 6DoF. In such embodiments, the 3D caption system 210 maytransition between tracking systems based on the availability of thetracked indicia to maintain consistent tracking in 6DoF.

The disruption detection component 606 monitors tracking indicia todetect disruptions. Upon the disruption detection component 606detecting an interruption of one or more indicia, such that tracking in6DoF becomes unreliable or impossible, the 3D caption system 210transitions to tracking the 3D caption in the 3D space in 3DoF in orderto prevent an interruption of the display. For example, the 3D captionsystem 210 may transition from a first tracking system (or first set oftracking systems among the set of tracking systems) to a second trackingsystem among the set of tracking systems (or second set of trackingsystems), wherein the second tracking system is capable of tracking the3D caption with 3DoF in the 3D space, based on the tracking indiciaavailable.

In some example embodiments, the set of tracking systems of the 3Dcaption system 210 includes a gyroscopic tracking system, an NFT system,as well as a SLAM tracking system. Each tracking system among the set oftracking systems may analyze tracking indicia in order to track aposition of a virtual object within a 3D space. For example, to track avirtual object with 6DoF, the 3D caption system 210 may require at leastsix tracking indicia to be available. As tracking indicia becomeobstructed or unavailable for various reasons, the 3D caption system 210may transition between the available tracking systems among the set oftracking systems in order to maintain 6DoF, or transition to 3DoF ifnecessary.

It will be readily appreciated that the 3D caption system 210 providesconsistent rendered virtual objects (e.g., 3D captions) in real-world 3Dspaces in a wide variety of environments and situations. In manyapplications it can be desirable to provide firm consistency for thelocations of these virtual objects as one or more users, cameras, orother tracking items move around in the environment. This can involvethe recognition and use of a specific fixed reference point (e.g., afixed surface) in the real-world environment. Not using a fixedreference point or item can result in floating or other undesirableinconsistencies in the rendering and presentation of the virtualobjects.

To ensure firm consistency in the location of virtual objects,annotation data in the example form of a presentation lens that isspecific for the 3D object tracking and rendering described herein maybe employed. In particular, a surface-aware lens is a presentation lensthat identifies and references a real-world surface (e.g., the ground)for the consistent rendering and presentation of virtual objects in 3Dspace. The surface-aware lens can be a specific portion or subcomponentwithin the rendering component 602. This surface-aware lens of therendering component 602 can be configured to recognize a referencesurface based on visual camera content, and may also utilize otherdevice inputs (e.g., gyroscope, accelerometer, compass) to determinewhat is an appropriate surface within a 3D space depicted in a livecamera feed. Once the reference surface has been determined, then avirtual object can be accomplished with respect to that referencesurface. In an example, the reference surface in the 3D space is aground surface. The 3D caption system 210 may render the 3D caption at aposition in the 3D space such that the caption appears to be on orslightly above the 3D space.

FIGS. 7-9 are a flowchart illustrating example operations of the 3Dcaption system in performing a method 700 for generating a message thatincludes a 3D caption, according to example embodiments. The method 700may be embodied in computer-readable instructions for execution by oneor more processors such that the operations of the method 700 may beperformed in part or in whole by the functional components of the 3Dcaption system 210; accordingly, the method 700 is described below byway of example with reference thereto. However, it shall be appreciatedthat at least some of the operations of the method 700 may be deployedon various other hardware configurations and the method 700 is notintended to be limited to the 3D caption system 210.

At operation 702, the annotation system 206 receives a first input toactivate a 3D caption lens. The 3D caption lens may be selected from agroup of lenses.

At operation 704, the 3D caption system 210 causes display of an editinginterface 212 on the client device 102. The editing interface 212enables a user to input one or more text characters that provide a basisfor a 3D caption. To this end, the editing interface 212 may include akeyboard to enable the user to input the one or more text characters.Text characters input by the user are initially displayed by the 3Dcaption system 210 as a two-dimensional (2D) overlay on a camera feedproduced by a camera of the client device 102.

At operation 706, the 3D caption system 210 receives a second inputcomprising one or more text characters input by a user of the clientdevice using the editing interface 212.

At operation 708, the 3D caption system 210 causes display of the one ormore text characters in the editing interface 212. As noted above, a 2Drepresentation of the one or more text characters is displayed in theediting interface 212 as an overlay on top of a camera feed produced bya camera of the client device 102. Example aspects of the editinginterface 212 are discussed below and illustrated in FIGS. 11, 12, and15A.

At operation 710, the 3D caption system 210 detects a third input, andin response to detecting the third input, the 3D caption system 210causes display of a preview interface 214, at operation 712. The thirdinput may, for example, include a motion-based input such as a change oforientation of the client device 102. For example, if the user ispointing the camera of the client device 102 at an upward orientation,the 2D representation of the one or more text characters is presented inthe editing interface 212. If the user changes the orientation of thecamera to be facing downward, the 3D caption system 210 may toggle fromdisplaying the editing interface 212 to displaying the preview interface214. By allowing users to toggle between the editing interface 212 andthe preview interface 214, rather than displaying additional buttons tofacilitate this functionality, the 3D caption system 210 provides aconvenient mechanism to toggle between interfaces that reducesconsumption of display area, which may be provide an advantage inimplementations on devices that have a limited display size.

The preview interface 214 includes a presentation of a 3D captiongenerated based on the one or more text characters input by the user.The 3D caption is a 3D representation of the one or more text charactersinput by the user. The 3D caption may be rendered at a position in a 3Dspace captured in the camera feed that is based on a detected referencesurface in the 3D space such as a ground or floor surface. For example,the 3D caption system may render the 3D caption such that it appears tobe attached to the detected reference surface.

While presenting the 3D caption within the preview interface 214, the 3Dcaption system 210 may detect movement of the client device that causesa second 3D space to be captured in the camera feed. The 3D captionsystem 210 may animate the 3D caption, moving from the first 3D space tothe second 3D space during the movement of the client device 102. Aspart of animating the movement of moving the 3D caption, the 3D captionsystem 210 may render the 3D caption with a lower opacity than whilestationary.

At operation 714, the messaging system 100 generates a message thatincludes one or more images having the rendered 3D caption overlaidthereon. In generating the message, the messaging system 100 may record(e.g., store in memory) one or more images from the camera feed with the3D caption applied. The messaging system 100 may further apply one ormore user-specified filters to the recorded image(s) in generating themessage. Upon recording the one or more images from the camera feed, themessaging system 100 may provide the user with the ability to cancelgeneration of the message (e.g., via one or more interface features). Ifthe user cancels generation of the message, the messaging system 100reverts to displaying the 3D caption within the preview interface 214.In this way, the messaging system 100 provides the user with an abilityto generate a new message without having to recreate the 3D caption.

As shown in FIG. 8, the method 700 may, in some embodiments, includeoperations 802, 804, 806, 808, 810, and 812. Consistent with theseembodiments, the operations 802, 804, 806, 808, 810, and 812 may beperformed as part of operation 712 (e.g., as a sub-routine orsub-operation) where the 3D caption system 210 causes display of apreview interface comprising a presentation of a 3D caption within areal-world environment captured within a camera feed.

At operation 802, the rendering component 602 detects a real-worldreference surface in 3D space depicted in a camera feed of a camera. Insome embodiments, the reference surface can be a user-specifiedreference surface. As such, the detecting of the reference surface isbased on user input such as a tap or other gesture to indicate areference surface. Such a reference surface can be the floor surface orthe ground surface in many cases, although other fixed and ascertainablesurfaces can also be used. For example, the rendering component 602 maydetermine the reference surface by identifying a fixed surface based onan analysis of visual camera content, and may also utilize other deviceinputs (e.g., gyroscope, accelerometer, compass) to ascertain what is anappropriate surface within a 3D space captured by the camera view. Invarious embodiments, a confirmation that the proper reference surfacehas been indicated or highlighted can be requested from the user. Insome situations, the system may indicate that a proper reference surfacecannot be detected, such that further input or help from the user may beneeded.

At operation 804, the rendering component 602 orients the 3D caption(e.g., generated based on user input) based on the detected referencesurface. The orienting of the 3D caption may include assigning the 3Dcaption to a position in 3D space based on the detected referencesurface, and identifying a set of tracking indicia to be used by thetracking system 604 in tracking the 3D caption in the 3D space. Theposition to which the 3D caption is assigned may correspond to thereference surface or a predefined distance above the reference surface.

At operation 806, the rendering component 602 renders the 3D captionwith respect to the reference surface. More specifically, the renderingof the 3D caption with respect to the reference surface may includerendering and maintaining the 3D caption at the assigned position withinthe 3D space. Thus, in instances in which the assigned position is apredefined distance from the reference surface, the rendering of the 3Dcaption may include rendering and maintaining the virtual object at thepredefined distance from the reference surface. In these instances, the3D caption, when rendered, may not actually appear to contact or restagainst the reference surface, but rather may appear to be hoveringabove or extending away from the reference surface at the predefineddistance.

At operation 808, the tracking system 604 tracks the 3D caption in 6DoFat the position in the 3D space via the first tracking sub-system 604A,or a combination of multiple tracking sub-systems (e.g., the firsttracking sub-system 604A and the second tracking sub-system 604B), basedon the identified set of tracking indicia. When tracking the virtualobject in 6DoF, a user viewing the object on the client device 102 canturn or move in any direction without disrupting tracking of the object.For example, the tracking system 604 may track the position of the 3Dcaption based on a combination of an NFT system and a gyroscopictracking system.

At operation 810, the disruption detection component 606 detects aninterruption of a tracking indicia from among the tracking indiciatracked by the tracking sub-systems (e.g., the first tracking sub-system604A). For example, the first tracking sub-system 604A may include a NFTsystem configured to rely on tracking indicia that include features ofan environment or active light sources in proximity to the 3D captionwithin the environment (e.g., the ground's plane, or the horizon). TheNFT system of the first tracking sub-system 604A may therefore rely onthe positions of three or more known features in the environment todetermine the position of the 3D caption relative to the client device102 in the three-dimensional space. Should any one or more of thetracking indicia tracked by the first tracking sub-system 604A becomeobstructed or unavailable, the tracking of the virtual object in the 3Dspace would become disrupted.

At operation 812 in response to the disruption detection component 606detecting the disruption of the one or more tracking indicia, thetracking system 604 transitions to one or more other trackingsub-systems (e.g., the second tracking sub-system 604B and/or the thirdtracking sub-system 604C) to maintain tracking of the 3D captionrelative to the client device 102 in the 3D space. In doing so, thetracking system 604 may transition from 6DoF to 3DoF, wherein 3DoFmeasures pitch, roll, and yaw, but does not measure translations. As thetracking indicia again become available, the tracking system 604 maytransition from 3DoF back to 6DoF. For example, when the NFT systembecomes unavailable, the tracking system 604 may utilize the lasttracking indicia gathered and tracked by the NFT system throughout thesubsequent 3DoF experience.

As shown in FIG. 9, the method 700 may, in some embodiments, includeoperations 902 and 904. In the embodiment illustrated in FIG. 9, theoperations 902 and 904 may be performed during the display of thepreview interface (e.g., prior to operation 714). In other embodiments,the operations 902 and 904 may be performed during display of theediting interface (e.g., subsequent to operation 704).

At operation 902, the 3D caption system 210 receives a fourth inputcomprising an edit to the presentation of the 3D caption. The edit may,for example, include a change to a scale, orientation, a position, font,color, or the substance of the 3D caption such as an addition of one ormore text characters or a deletion of one or more text characters. Thefourth input may include one of many types of input such as keyboardinput, motion-based input, or touchscreen gestures. For example, theuser may use a pinch gesture to change the scale of the 3D caption. Asanother example, the user may use a two-finger rotation gesture tochange the orientation of the 3D caption. A change to the substance ofthe 3D caption may include a removal or addition of one or more textcharacters to the 3D caption using the keyboard.

At operation 904, the 3D caption system 210 updates the presentation ofthe 3D caption based on the fourth input. The updating of thepresentation of the 3D caption may, for example, include changing ascale, orientation, a position, font, or color, adding one or more textcharacters, removing one or more text characters, or otherwise changingthe substance of the 3D caption in accordance with the user edit.

FIG. 10 is an interface diagram that illustrates a user interface 1000provided by the messaging system 100, according to some embodiments.User interface 1000 includes a lens carousel from which a user mayinitiate functionality of the 3D caption system 210 through selection oficon 1002. As shown, the lens carousel is overlaid upon a 3D spacecaptured within a camera feed produced by a camera of a computing device(e.g., a client device 102).

Consistent with some embodiments, upon receiving a user selection of theicon 1002, a user is presented with an editing interface configured forcreating and editing a 3D caption. For example, upon receiving a userselection of the icon 1102, the 3D caption system 210 may cause displayof a user interface 1100 illustrated in FIG. 11. As shown in FIG. 11,the user interface 1100 includes a keyboard and a blinking cursoroverlaid upon the 3D space captured within the camera feed. The user mayuse the keyboard to input one or more text characters that provide abasis for a 3D caption to be rendered within the 3D space. The userinterface 1100 is an example of the editing interface 212.

As shown in FIG. 12, upon receiving input from the user (e.g., enteredvia the keyboard), the user interface 1100 is updated to present arepresentation of the input text (“Typing on the screen”). Within theuser interface 1100, a 2D representation of the user input is renderedat the foreground of the camera feed of the client device 102. Inessence, the 2D representation of the user input is a 2D representationof a 3D caption. In other words, the 2D representation of the user inputis a preview of the 3D caption.

Consistent with some embodiments, a user of the client device 102 mayaccess a preview interface (e.g., preview interface 214) that includes apreview of the 3D caption by providing an input such as changing anorientation of the client device 102 (e.g., changing the orientation ofthe camera from pointing upward to pointing downward) or by selecting aninterface element (e.g., a button) presented within the previewinterface 214.

FIG. 13 illustrates an interface 1300 that includes a preview of a 3Dcaption generated based on user input (e.g., user input provided via theinterface 1100). The interface 1300 is an example of the previewinterface 214. As noted above, the user may access the interface 1300 byproviding an input such as a change in orientation. As shown in FIG. 13,upon detecting a reference surface (e.g., the ground) in the 3D spacecaptured within the camera feed (e.g., based on a change of orientationof the computing device), a 3D caption based on the user's authored textis rendered within the 3D space captured within the camera feed. Asshown, the 3D text object is rendered with respect to a referencesurface in the 3D space. That is, the 3D text object, as rendered, isoriented within the 3D space at a position relative to the referencesurface (e.g., the ground). Rendering the 3D object in this manner makesit appear attached to a real-world surface captured within the camerafeed.

As shown in FIG. 14, the interface 1300 allows a user edit (e.g., usinga keyboard) the 3D caption while it is rendered within the 3D spacecaptured within the camera feed. For example, as shown, the user hasedited the 3D caption by deleting multiple characters.

FIG. 15A illustrates an interface 1500, which is an example of theediting interface 212, that includes a keyboard and a 2D representationof user input entered via the keyboard. In this example, the user inputcomprises multiple emojis (e.g., a small digital image or icon used toexpress an idea, emotion, etc., in electronic communication). Initially,as shown in FIG. 15A, a 2D representation of the emojis are presented asan overlay at the foreground of a camera feed of the client device 102.

FIG. 15B illustrates an interface 1550 comprising a view of a 3D captiongenerated based on the user input discussed above in reference to FIG.15A. The interface 1550 is an example of the preview interface 214. Theuser may access the interface 1550 from the interface 1500 by providingappropriate input such as a change in orientation of the client device102. Within the interface 1550, the 3D caption is rendered with respectto a detected reference surface (e.g., a table top).

FIGS. 16A-16C illustrate an interface 1600, which is an example of thepreview interface 214. As shown in FIGS. 16A-16C, as a user is editing a3D caption while accessing the preview interface 214, the user may movethe computing device away from the caption and the 3D caption system 210is able to track the movement and force the 3D caption to follow withinthe 3D space captured within the camera feed of the computing device.For example, the 3D caption system 210 may detect movement of the clientdevice that causes a second 3D space to be captured in the camera feedand animate the 3D caption moving from the first 3D space to the second3D space during the movement of the client device. In this manner, the3D caption system 210 ensures that, while editing, the 3D captionremains visible to the user until they commit a final version of the 3Dcaption. As shown, moving the 3D caption may be rendered with a loweropacity than remaining stationary.

FIGS. 17A-17D are interface diagrams that illustrate an interface 1700,which is an example of a preview interface 214. As shown in FIG. 17A, a3D caption 1702 is rendered within a 3D space at a first position; the3D caption 1702 is rendered such that it appears attached to a referencesurface (e.g., the ground). As shown in FIG. 17B, through appropriateinteraction with the 3D caption 1702 (e.g., a select and drag gesture),the user may move the 3D caption 1702 such that it is rendered at asecond position within the 3D space.

As shown in FIGS. 17C and 17D, a user may change a scale and rotation ofthe 3D caption 1702 through appropriate interaction with the 3D caption1702. For example, the user can perform a pinch and rotate gesture withtwo fingers on an input touchscreen display on which the camera feed isdisplayed to scale and rotate the 3D caption 1702 on the referencesurface without affecting a layout of the 3D caption 1702.

Once the user is satisfied with the placement and look of a 3D caption,the user may create a message that includes the 3D caption and one ormore images from the camera feed. For example, the user may use theclient device 102 to record a video in which the 3D caption is renderedsuch that it appears attached to a surface in the video.

As shown in FIGS. 18A and 18B, as part of creating the message, the usermay be presented with a menu or other interface element that allows theuser to select and apply one or more filters to apply to images of thecamera feed along with the 3D caption rendered in the 3D space capturedwithin the camera view.

FIG. 19 is a block diagram illustrating an example software architecture1906, which may be used in conjunction with various hardwarearchitectures herein described. FIG. 19 is a non-limiting example of asoftware architecture and it will be appreciated that many otherarchitectures may be implemented to facilitate the functionalitydescribed herein. The software architecture 1906 may execute on hardwaresuch as machine 2000 of FIG. 20 that includes, among other things,processors 2004, memory 2014, and input/output (I/O) components 2018. Arepresentative hardware layer 1952 is illustrated and can represent, forexample, the machine 2000 of FIG. 20. The representative hardware layer1952 includes a processing unit 1954 having associated executableinstructions 1904. Executable instructions 1904 represent the executableinstructions of the software architecture 1906, including implementationof the methods, components, and so forth described herein. The hardwarelayer 1952 also includes memory and/or storage modules memory/storage1956, which also have executable instructions 1904. The hardware layer1952 may also comprise other hardware 1958.

In the example architecture of FIG. 19, the software architecture 1906may be conceptualized as a stack of layers where each layer providesparticular functionality. For example, the software architecture 1906may include layers such as an operating system 1902, libraries 1920,applications 1916, frameworks/middleware 1918, and a presentation layer1914. Operationally, the applications 1916 and/or other componentswithin the layers may invoke API calls 1908 through the software stackand receive a response as in messages 1919 to the API calls 1908. Thelayers illustrated are representative in nature and not all softwarearchitectures have all layers. For example, some mobile or specialpurpose operating systems may not provide a frameworks/middleware 1918,while others may provide such a layer. Other software architectures mayinclude additional or different layers.

The operating system 1902 may manage hardware resources and providecommon services. The operating system 1902 may include, for example, akernel 1922, services 1924, and drivers 1926. The kernel ay act as anabstraction layer between the hardware and the other software layers.For example, the kernel 1922 may be responsible for memory management,processor management (e.g., scheduling), component management,networking, security settings, and so on. The services 1924 may provideother common services for the other software layers. The drivers 1926are responsible for controlling or interfacing with the underlyinghardware. For instance, the drivers 1926 include display drivers, cameradrivers, Bluetooth® drivers, flash memory drivers, serial communicationdrivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers,audio drivers, power management drivers, and so forth depending on thehardware configuration.

The libraries 1920 provide a common infrastructure that is used by theapplications 1916 and/or other components and/or layers. The libraries1920 provide functionality that allows other software components toperform tasks in an easier fashion than to interface directly with theunderlying operating system 1902 functionality (e.g., kernel 1922,services 1924 and/or drivers 1926). The libraries 1920 may includesystem libraries 1944 (e.g., C standard library) that may providefunctions such as memory allocation functions, string manipulationfunctions, mathematical functions, and the like. In addition, thelibraries 1920 may include API libraries 1946 such as media libraries(e.g., libraries to support presentation and manipulation of variousmedia format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphicslibraries (e.g., an OpenGL framework that may be used to render 2D and3D in a graphic content on a display), database libraries (e.g., SQLitethat may provide various relational database functions), web libraries(e.g., WebKit that may provide web browsing functionality), and thelike. The libraries 1920 may also include a wide variety of otherlibraries 1948 to provide many other APIs to the applications 1916 andother software components/modules.

The frameworks/middleware 1918 (also sometimes referred to asmiddleware) provide a higher-level common infrastructure that may beused by the applications 1916 and/or other software components/modules.For example, the frameworks/middleware 1918 may provide various graphicuser interface (GUI) functions, high-level resource management,high-level location services, and so forth. The frameworks/middleware1918 may provide a broad spectrum of other APIs that may be utilized bythe applications 1916 and/or other software components/modules, some ofwhich may be specific to a particular operating system 1902 or platform.

The applications 1916 include built-in applications 1938 and/orthird-party applications 1940. Examples of representative built-inapplications 1938 may include, but are not limited to, a contactsapplication, a browser application, a book reader application, alocation application, a media application, a messaging application,and/or a game application. Third-party applications 1940 may include anapplication developed using the ANDROID™ or IOS™ software developmentkit (SDK) by an entity other than the vendor of the particular platform,and may be mobile software running on a mobile operating system such asIOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. Thethird-party applications 1940 may invoke the API calls 1908 provided bythe mobile operating system (such as operating system 1902) tofacilitate functionality described herein.

The applications 1916 may use built-in operating system functions (e.g.,kernel 1922, services 1924, and/or drivers 1926), libraries 1920, andframeworks/middleware 1918 to create user interfaces to interact withusers of the system. Alternatively, or additionally, in some systemsinteractions with a user may occur through a presentation layer, such aspresentation layer 1914. In these systems, the application/component“logic” can be separated from the aspects of the application/componentthat interact with a user.

FIG. 20 is a block diagram illustrating components of a machine 2000,according to some example embodiments, able to read instructions from amachine-readable medium (e.g., a machine-readable storage medium) andperform any one or more of the methodologies discussed herein.Specifically, FIG. 20 shows a diagrammatic representation of the machine2000 in the example form of a computer system, within which instructions2010 (e.g., software, a program, an application, an applet, an app, orother executable code) for causing the machine 2000 to perform any oneor more of the methodologies discussed herein may be executed. As such,the instructions 2010 may be used to implement modules or componentsdescribed herein. The instructions 2010 transform the general,non-programmed machine 2000 into a particular machine 2000 programmed tocarry out the described and illustrated functions in the mannerdescribed. In alternative embodiments, the machine 2000 operates as astandalone device or may be coupled (e.g., networked) to other machines.In a networked deployment, the machine 2000 may operate in the capacityof a server machine or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine 2000 may comprise, but not be limitedto, a server computer, a client computer, a personal computer (PC), atablet computer, a laptop computer, a netbook, a set-top box (STB), apersonal digital assistant (PDA), an entertainment media system, acellular telephone, a smart phone, a mobile device, a wearable device(e.g., a smart watch), a smart home device (e.g., a smart appliance),other smart devices, a web appliance, a network router, a networkswitch, a network bridge, or any machine capable of executing theinstructions 2010, sequentially or otherwise, that specify actions to betaken by machine 2000. Further, while only a single machine 2000 isillustrated, the term “machine” shall also be taken to include acollection of machines that individually or jointly execute theinstructions 2010 to perform any one or more of the methodologiesdiscussed herein.

The machine 2000 may include processors 2004, memory memory/storage2006, and I/O components 2018, which may be configured to communicatewith each other such as via a bus 2002. In an example embodiment, theprocessors 2004 (e.g., a central processing unit (CPU), a reducedinstruction set computing (RISC) processor, a complex instruction setcomputing (CISC) processor, a graphics processing unit (GPU), a digitalsignal processor (DSP), an application-specific integrated circuit(ASIC), a radio-frequency integrated circuit (RFIC), another processor,or any suitable combination thereof) may include, for example, aprocessor 2008 and a processor 2012 that may execute the instructions2010. The term “processor” is intended to include multi-core processors2004 that may comprise two or more independent processors (sometimesreferred to as “cores”) that may execute instructions 2010contemporaneously. Although FIG. 20 shows multiple processors 2004, themachine 2000 may include a single processor with a single core, a singleprocessor with multiple cores (e.g., a multi-core processor), multipleprocessors with a single core, multiple processors with multiple cores,or any combination thereof.

The memory/storage 2006 may include a memory 2014, such as a mainmemory, or other memory storage, and a storage unit 2016, bothaccessible to the processors 2004 such as via the bus 2002. The storageunit 2016 and memory 2014 store the instructions 2010 embodying any oneor more of the methodologies or functions described herein. Theinstructions 2010 may also reside, completely or partially, within thememory 2014, within the storage unit 2016, within at least one of theprocessors 2004 (e.g., within the processor's cache memory), or anysuitable combination thereof, during execution thereof by the machine2000. Accordingly, the memory 2014, the storage unit 2016, and thememory of processors 2004 are examples of machine-readable media.

The I/O components 2018 may include a wide variety of components toreceive input, provide output, produce output, transmit information,exchange information, capture measurements, and so on. The specific I/O:components 2018 that are included in a particular machine 2000 willdepend on the type of machine. For example, portable machines such asmobile phones will likely include a touch input device or other suchinput mechanisms, while a headless server machine will likely notinclude such a touch input device. It will be appreciated that the I/Ocomponents 2018 may include many other components that are not shown inFIG. 20. The I/O components 2018 are grouped according to functionalitymerely for simplifying the following discussion and the grouping is inno way limiting. In various example embodiments, the components 2018 mayinclude output components 2026 and input components 2028. The outputcomponents 2026 may include visual components (e.g., a display such as aplasma display panel (PDP, a light emitting diode (LED) display, aliquid crystal display (LCD), a projector, or a cathode ray tube (CRT)),acoustic components (e.g., speakers), haptic components (e.g., avibratory motor, resistance mechanisms), other signal generators, and soforth. The input components 2028 may include alphanumeric inputcomponents (e.g., a keyboard, a touch screen configured to receivealphanumeric input, a photo-optical keyboard, or other alphanumericinput components), point based input components (e.g., a mouse, atouchpad, a trackball, a joystick, a motion sensor, or other pointinginstrument), tactile input components (e.g., a physical button, a touchscreen that provides location and/or force of touches or touch gestures,or other tactile input components), audio input components (e.g., amicrophone), and the like.

In further example embodiments, the I/O components 2018 may includebiometric components 2030, motion components 2034, environmentalcomponents 2036, or position components 2038 among a wide array of othercomponents. For example, the biometric components 2030 may includecomponents to detect expressions (e.g., hand expressions, facialexpressions, vocal expressions, body gestures, or eye tracking), measurebiosignals (e.g., blood pressure, heart rate, body temperature,perspiration, or brain waves), identify a person (e.g., voiceidentification, retinal identification, facial identification,fingerprint identification, or electroencephalogram basedidentification), and the like. The motion components 2034 may includeacceleration sensor components (e.g., accelerometer), gravitation sensorcomponents, rotation sensor components (e.g., gyroscope), and so forth.The environmental components 2036 may include, for example, illuminationsensor components (e.g., photometer), temperature sensor components(e.g., one or more thermometer that detect ambient temperature),humidity sensor components, pressure sensor components (e.g.,barometer), acoustic sensor components (e.g., one or more microphonesthat detect background noise), proximity sensor components infraredsensors that detect nearby objects), gas sensors (e.g., gas detectionsensors to detection concentrations of hazardous gases for safety or tomeasure pollutants in the atmosphere), or other components that mayprovide indications, measurements, or signals corresponding to asurrounding physical environment. The position components 2038 mayinclude location sensor components (e.g., a GPS receiver component),altitude sensor components (e.g., altimeters or barometers that detectair pressure from which altitude may be derived), orientation sensorcomponents (e.g., magnetometers), and the like.

Communication may be implemented using a wide variety of technologies.The components 2018 may include communication components 2040 operableto couple the machine 2000 to a network 2032 or devices 2020 viacoupling 2024 and coupling 2022, respectively. For example, thecommunication components 2040 may include a network interface componentor other suitable device to interface with the network 2032. In furtherexamples, communication components 2040 may include wired communicationcomponents, wireless communication components, cellular communicationcomponents, Near Field Communication (NFC) components, Bluetooth®components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and othercommunication components to provide communication via other modalities.The devices 2020 may be another machine or any of a wide variety ofperipheral devices (e.g., a peripheral device coupled via a USB).

Moreover, the communication components 2040 may detect identifiers orinclude components operable to detect identifiers. For example, thecommunication components 2040 may include Radio Frequency Identification(RFID) tag reader components, NFC smart tag detection components,optical reader components (e.g., an optical sensor to detectone-dimensional bar codes such as Universal Product Code (UPC) bar code,multi-dimensional bar codes such as Quick Response (QR) code, Azteccode, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2Dbar code, and other optical codes), or acoustic detection components(e.g., microphones to identify tagged audio signals). In addition, avariety of information may be derived via the communication components2040, such as, location via Internet Protocol (IP) geo-location,location via Wi-Fi® signal triangulation, location via detecting a NFCbeacon signal that may indicate a particular location, and so forth.

GLOSSARY

“CARRIER SIGNAL” in this context refers to any intangible medium that iscapable of storing, encoding, or carrying instructions for execution bythe machine, and includes digital or analog communications signals orother intangible medium to facilitate communication of suchinstructions. Instructions may be transmitted or received over thenetwork using a transmission medium via a network interface device andusing any one of a number of well-known transfer protocols.

“CLIENT DEVICE” in this context refers to any machine that interfaces toa communications network to obtain resources from one or more serversystems or other client devices. A client device may be, but is notlimited to, a mobile phone, desktop computer, laptop, PDAs, smartphones, tablets, ultra books, netbooks, laptops, multi-processorsystems, microprocessor-based or programmable consumer electronics, gameconsoles, set-top boxes, or any other communication device that a usermay use to access a network.

“COMMUNICATIONS NETWORK” in this context refers to one or more portionsof a network that may be an ad hoc network, an intranet, an extranet, avirtual private network (TN), a local area network (LAN), a wireless LAN(WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitanarea network (MAN), the Internet, a portion of the Internet, a portionof the Public Switched Telephone Network (PSTN), a plain old telephoneservice (POTS) network, a cellular telephone network, a wirelessnetwork, a Wi-Fi® network, another type of network, or a combination oftwo or more such networks. For example, a network or a portion of anetwork may include a wireless or cellular network and the coupling maybe a Code Division Multiple Access (CDMA) connection, a Global Systemfor Mobile communications (GSM) connection, or other type of cellular orwireless coupling. In this example, the coupling may implement any of avariety of types of data transfer technology, such as Single CarrierRadio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO)technology, General Packet Radio Service (GPRS) technology, EnhancedData rates for GSM Evolution (EDGE) technology, third GenerationPartnership Project (3GPP) including 3G, fourth generation wireless (4G)networks, Universal Mobile Telecommunications System (UMTS), High SpeedPacket Access (HSPA), Worldwide Interoperability for Microwave Access(WiMAX), Long Term Evolution (LTE) standard, others defined by variousstandard setting organizations, other long range protocols, or otherdata transfer technology.

“EPHEMERAL MESSAGE” in this context refers to a message that isaccessible for a time-limited duration. An ephemeral message may be atext, an image, a video, and the like. The access time for the ephemeralmessage may be set by the message sender. Alternatively, the access timemay be a default setting or a setting specified by the recipient.Regardless of the setting technique, the message is transitory.

“MACHINE-READABLE MEDIUM” in this context refers to a component, deviceor other tangible media able to store instructions and data temporarilyor permanently and may include, but is not be limited to, random-accessmemory (RAM), read-only memory (ROM), buffer memory, flash memory,optical media, magnetic media, cache memory, other types of storage(e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or anysuitable combination thereof. The term “machine-readable medium” shouldbe taken to include a single medium or multiple media (e.g., acentralized or distributed database, or associated caches and servers)able to store instructions. The term “machine-readable medium” shallalso be taken to include any medium, or combination of multiple media,that is capable of storing instructions (e.g., code) for execution by amachine, such that the instructions, when executed by one or moreprocessors of the machine, cause the machine to perform any one or moreof the methodologies described herein. Accordingly, a “machine-readablemedium” refers to a single storage apparatus or device, as well as“cloud-based” storage systems or storage networks that include multiplestorage apparatus or devices. The term “machine-readable medium”excludes signals per se.

“COMPONENT” in this context refers to a device, physical entity, orlogic having boundaries defined by function or subroutine calls, branchpoints, APIs, or other technologies that provide for the partitioning ormodularization of particular processing or control functions. Componentsmay be combined via their interfaces with other components to carry outa machine process. A component may be a packaged functional hardwareunit designed for use with other components and a part of a program thatusually performs a particular function of related functions. Componentsmay constitute either software components (e.g., code embodied on amachine-readable medium) or hardware components.

A “hardware component” is a tangible unit capable of performing certainoperations and may be configured or arranged in a certain physicalmanner. In various example embodiments, one or more computer systems(e.g., a standalone computer system, a client computer system, or aserver computer system) or one or more hardware components of a computersystem (e.g., a processor or a group of processors) may be configured bysoftware (e.g., an application or application portion) as a hardwarecomponent that operates to perform certain operations as describedherein. A hardware component may also be implemented mechanically,electronically, or any suitable combination thereof. For example, ahardware component may include dedicated circuitry or logic that ispermanently configured to perform certain operations. A hardwarecomponent may be a special-purpose processor, such as aField-Programmable Gate Array (FPGA) or an Application SpecificIntegrated Circuit (ASIC). A hardware component may also includeprogrammable logic or circuitry that is temporarily configured bysoftware to perform certain operations. For example, a hardwarecomponent may include software executed by a general-purpose processoror other programmable processor.

Once configured by such software, hardware components become specificmachines (or specific components of a machine) uniquely tailored toperform the configured functions and are no longer general-purposeprocessors. It will be appreciated that the decision to implement ahardware component mechanically, in dedicated and permanently configuredcircuitry, or in temporarily configured circuitry (e.g., configured bysoftware) may be driven by cost and time considerations. Accordingly,the phrase “hardware component” (or “hardware-implemented component”)should be understood to encompass a tangible entity, be that an entitythat is physically constructed, permanently configured (e.g.,hardwired), or temporarily configured (e.g., programmed) to operate in acertain manner or to perform certain operations described herein.

Considering embodiments in which hardware components are temporarilyconfigured (e.g., programmed), each of the hardware components need notbe configured or instantiated at any one instance in time. For example,where a hardware component comprises a general-purpose processorconfigured by software to become a special-purpose processor, thegeneral-purpose processor may be configured as respectively differentspecial-purpose processors (e.g., comprising different hardwarecomponents) at different times. Software accordingly configures aparticular processor or processors, for example, to constitute aparticular hardware component at one instance of time and to constitutea different hardware component at a different instance of time.

Hardware components can provide information to, and receive informationfrom, other hardware components. Accordingly, the described hardwarecomponents may be regarded as being communicatively coupled. Wheremultiple hardware components exist contemporaneously, communications maybe achieved through signal transmission (e.g., over appropriate circuitsand buses) between or among two or more of the hardware components. Inembodiments in which multiple hardware components are configured orinstantiated at different times, communications between such hardwarecomponents may be achieved, for example, through the storage andretrieval of information in memory structures to which the multiplehardware components have access. For example, one hardware component mayperform an operation and store the output of that operation in a memorydevice to which it is communicatively coupled. A further hardwarecomponent may then, at a later time, access the memory device toretrieve and process the stored output. Hardware components may alsoinitiate communications with input or output devices, and can operate ona resource (e.g., a collection of information).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implementedcomponents that operate to perform one or more operations or functionsdescribed herein. As used herein, “processor-implemented component”refers to a hardware component implemented using one or more processors.Similarly, the methods described herein may be at least partiallyprocessor-implemented, with a particular processor or processors beingan example of hardware. For example, at least some of the operations ofa method may be performed by one or more processors orprocessor-implemented components. Moreover, the one or more processorsmay also operate to support performance of the relevant operations in a“cloud computing” environment or as a “software as a service” (SaaS).For example, at least some of the operations may be performed by a groupof computers (as examples of machines including processors), with theseoperations being accessible via a network (e.g., the Internet) and viaone or more appropriate interfaces (e.g., an API). The performance ofcertain of the operations may be distributed among the processors, notonly residing within a single machine, but deployed across a number ofmachines. In some example embodiments, the processors orprocessor-implemented components may be located in a single geographiclocation (e.g., within a home environment, an office environment, or aserver farm). In other example embodiments, the processors orprocessor-implemented components may be distributed across a number ofgeographic locations.

“PROCESSOR” in this context refers to any circuit or virtual circuit (aphysical circuit emulated by logic executing on an actual processor)that manipulates data values according to control signals (e.g.,“commands”, “op codes”, “machine code”, etc.) and which producescorresponding output signals that are applied to operate a machine. Aprocessor may, for example, be a Central Processing Unit (CPU), aReduced Instruction Set Computing (RISC) processor, a ComplexInstruction Set Computing (CISC) processor, a Graphics Processing Unit(GPU), a Digital Signal Processor (DSP), an ASIC, a Radio-FrequencyIntegrated Circuit (RFIC) or any combination thereof. A processor mayfurther be a multi-core processor having two or more independentprocessors (sometimes referred to as “cores”) that may executeinstructions contemporaneously.

“TIMESTAMP” in this context refers to a sequence of characters orencoded information identifying when a certain event occurred, forexample giving a date and time of day, sometimes accurate to a smallfraction of a second.

What is claimed is:
 1. A system comprising: at least one hardwareprocessor; a memory storing instructions which, when executed by the atleast one hardware processor, cause the at least one hardware processorto perform operations comprising: causing display, on a display deviceof a client device, of a three-dimensional (3D) caption editinginterface, the 3D caption editing interface including a keyboarddisplayed in conjunction with a view of a camera feed of the clientdevice; receiving a first input comprising one or more text charactersentered via the keyboard; in response to receiving the first input,causing display of a two-dimensional (2D) representation of the one ormore text characters within the editing interface, the 2D representationof the one or more text characters being overlaid on the view of thecamera feed; in response to detecting a second input, causing display ofa preview interface, the causing the display of the preview interfacecomprising rendering a 3D caption based on the one or more textcharacters at a position in a first 3D space captured within the camerafeed; generating a message that includes the 3D caption rendered at theposition in the first 3D space captured within the camera feed;detecting movement of the client device that causes a second 3D space tobe captured in the camera feed; and animating the 3D caption moving fromthe first 3D space to the second 3D space during the movement of theclient device.
 2. The system of claim 1, wherein the causing the displayof the preview interface further comprises: detecting a referencesurface in the first 3D space captured within the camera feed; andorienting the 3D caption at the position in the first 3D space based onthe detected reference surface.
 3. The system of claim 2, whereinorienting the 3D caption at the position in the 3D space comprises:assigning the 3D caption to the position in the first 3D space based onthe detected reference surface; and identifying tracking indiciaoperable to track the 3D caption in the first 3D space.
 4. The system ofclaim 3, wherein the operations further comprise: tracking, by a firsttracking subsystem from among a set of tracking subsystems, the 3Dcaption at the position in the first 3D space using the trackingindicia; detecting an interruption of the tracking indicia; and inresponse to detecting the interruption of the tracking indicia, trackingthe 3D caption at the position in the first 3D space via a secondtracking subsystem from among the set of tracking subsystems.
 5. Thesystem of claim 1; wherein the operations further comprise: receiving athird input indicative of an edit to the 3D caption; and updating the 3Dcaption based on the edit.
 6. The system of claim 5, wherein the edit tothe 3D caption comprises one or more of: an additional text character, adeletion of one or more text characters corresponding to the firstinput, a scale change, an orientation change, a placement change, a fontchange, or a color change.
 7. The system of claim 1, wherein the secondinput comprises a change of orientation of the client device.
 8. Thesystem of claim 1, wherein the operations further comprise: receiving athird input to activate a 3D caption lens, wherein the causing of thedisplay of the 3D caption editing interface is in response to the thirdinput.
 9. A method comprising: causing display, on a display device of aclient device, of a three-dimensional (3D) caption editing interface,the 3D caption editing interface including a keyboard displayed inconjunction with a view of a camera feed of the client device; receivinga first input comprising one or more text characters entered via thekeyboard; in response to receiving the first input, causing display of atwo-dimensional (2D) representation of the one or more text characterswithin the editing interface, the 2D representation of the one or moretext characters being overlaid on the view of the camera feed; inresponse to detecting a second input, causing display of a previewinterface, the causing the display of the preview interface comprisingrendering a 3D caption based on the one or more text characters at aposition in a first 3D space captured within the camera feed; andgenerating, using one or more processors of a machine, a message thatincludes the 3D caption rendered at the position in the first 3D spacecaptured within the camera feed detecting movement of the client devicethat causes a second 3D space to be captured in the camera feed; andanimating the 3D caption moving from the first 3D space to the second 3Dspace during the movement of the client device.
 10. The method of claimof claim 9, wherein the causing the display of the preview interfacefurther comprises: detecting a reference surface in the first 3D spacecaptured within the camera feed; and orienting the 3D caption at theposition in the first 3D space based on the detected reference surface.11. The method of claim 10, wherein orienting the 3D caption at theposition in the 3D space comprises: assigning the 3D caption to theposition in first 3D space based on the detected reference surface; andidentifying tracking indicia operable to track the 3D caption in thefirst 3D space.
 12. The method of claim 11, wherein the operationsfurther comprise: tracking, by a first tracking subsystem from among aset of tracking subsystems, the 3D caption at the position in the first3D space using the tracking indicia; detecting an interruption of thetracking indicia; and in response to detecting the interruption of thetracking indicia, tracking the 3D caption at the position in the first3D space via a second tracking subsystem from among the set of trackingsubsystems.
 13. The method of claim 9, further comprising: receiving athird input indicative of an edit to the 3D caption; and updating the 3Dcaption based on the edit.
 14. The method of claim 13, wherein the editto the 3D caption comprises one or more of: an additional textcharacter, a deletion of one or more text characters corresponding tothe first input, a scale change, an orientation change, a placementchange, a font change, or a color change.
 15. The method of claim 9,wherein the second input comprises a change of orientation of the clientdevice.
 16. The method of claim 9, further comprising: receiving a thirdinput to activate a 3D caption lens, wherein the causing of the displayof the 3D caption editing interface is in response to the third input.17. A machine-readable medium storing instructions which, when executedby one or more processors of a machine, cause the machine to performoperations comprising: causing display, on a display device of a clientdevice, of a three-dimensional (3D) caption editing interface, the 3Dcaption editing interface including a keyboard displayed in conjunctionwith a view of a camera feed of the client device; receiving a firstinput comprising one or more text characters entered via the keyboard;in response to receiving the first input, causing display of atwo-dimensional (2D) representation of the one or more text characterswithin the editing interface, the 2D representation of the one or moretext characters being overlaid on the view of the camera feed; inresponse to detecting a second input, causing display of a previewinterface, the causing the display of the preview interface comprisingrendering a 3D caption based on the one or more text characters at aposition in a first 3D space captured within the camera feed; andgenerating a message that includes the 3D caption rendered at theposition in the first 3D space captured within the camera feed detectingmovement of the client device that causes a second 3D space to becaptured in the camera feed; and animating the 3D caption moving fromthe first 3D space to the second 3D space during the movement of theclient device.
 18. The machine-readable medium of claim 17, wherein thecausing the display of the preview interface further comprises:detecting a reference surface in the first 3D space captured within thecamera feed; assigning the 3D caption to the position in the first 3Dspace based on the detected reference surface; identifying trackingindicia operable to track the 3D caption in the first 3D space; andtracking, by a first tracking subsystem from among a set of trackingsubsystems, the first 3D caption at the position in the 3D space usingthe tracking indicia.